SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C

C static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C code

  • All rules 315
  • Vulnerability13
  • Bug76
  • Security Hotspot19
  • Code Smell207

  • Quick Fix 19
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. "sprintf" should not be used

           Security Hotspot
        3. Changing working directories without verifying the success is security-sensitive

           Security Hotspot
        4. Setting capabilities is security-sensitive

           Security Hotspot
        5. Using "tmpnam", "tmpnam_s" or "tmpnam_r" is security-sensitive

           Security Hotspot
        6. Using "strncpy" or "wcsncpy" is security-sensitive

           Security Hotspot
        7. Using "strncat" or "wcsncat" is security-sensitive

           Security Hotspot
        8. Using "strcat" or "wcscat" is security-sensitive

           Security Hotspot
        9. Using "strlen" or "wcslen" is security-sensitive

           Security Hotspot
        10. Changing directories improperly when using "chroot" is security-sensitive

           Security Hotspot
        11. Using "strcpy" or "wcscpy" is security-sensitive

           Security Hotspot
        12. Using publicly writable directories is security-sensitive

           Security Hotspot
        13. Using clear-text protocols is security-sensitive

           Security Hotspot
        14. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        15. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        16. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        17. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        18. Hard-coded passwords are security-sensitive

           Security Hotspot
        19. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Using "tmpnam", "tmpnam_s" or "tmpnam_r" is security-sensitive

        consistency - conventional
        security
        Security Hotspot
        • cwe
        • cert

        The functions "tmpnam", "tmpnam_s" and "tmpnam_r" are all used to return a file name that does not match an existing file, in order for the application to create a temporary file. However, even if the file did not exist at the time those functions were called, it might exist by the time the application tries to use the file name to create the files. This has been used by hackers to gain access to files that the application believed were trustworthy.

        There are alternative functions that, in addition to creating a suitable file name, create and open the file and return the file handler. Such functions are protected from this attack vector and should be preferred. About the only reason to use these functions would be to create a temporary folder, not a temporary file.

        Additionally, these functions might not be thread-safe, and if you don’t provide them buffers of sufficient size, you will have a buffer overflow.

        Ask Yourself Whether

        • There is a possibility that several threads call any of these functions simultaneously
        • There is a possibility that the resulting file is opened without forcing its creation, meaning that it might have unexpected access rights
        • The buffers passed to these functions are respectively smaller than
          • L_tmpnam for tmpnam
          • L_tmpnam_s for tmpnam_s
          • L_tmpnam for tmpnam_r

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • Use a function that directly opens the temporary file, such a tmpfile, tmpfile_s, mkstemp or mkstemps (the last two allow more accurate control of the file name).
        • If you can’t get rid of these functions, when using the generated name to open the file, use a function that forces the creation of the file and fails if the file already exists.

        Sensitive Code Example

        int f(char *tempData) {
          char *path = tmpnam(NULL); // Sensitive
          FILE* f = fopen(tmpnam, "w");
          fputs(tempData, f);
          fclose(f);
        }
        

        Compliant Solution

        int f(char *tempData) {
          // The file will be opened in "wb+" mode, and will be automatically removed on normal program exit
          FILE* f = tmpfile(); // Compliant
          fputs(tempData, f);
          fclose(f);
        }
        

        See

        • OWASP - Top 10 2021 Category A1 - Broken Access Control
        • OWASP - Top 10 2021 Category A6 - Vulnerable and Outdated Components
        • OWASP - Top 10 2017 Category A9 - Using Components with Known Vulnerabilities
        • CWE - CWE-377 - Insecure Temporary File
        • CERT, CON33-C. - Avoid race conditions when using library functions
        • CERT, FIO21-C. - Do not create temporary files in shared directories
        • STIG Viewer - Application Security and Development: V-222567 - The application must not be vulnerable to race conditions.
        • STIG Viewer - Application Security and Development: V-222612 - The application must not be vulnerable to overflow attacks.
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use